---
title: "Mode of Transport & Mode of Transport Detail"
space: "Clearing & Forwarding "
url: "https://support.aakvatech.com/Clearing & Forwarding /mode-of-transport"
updated: "2026-07-22"
---


<h2>1. Overview</h2>
<p>The <strong>Mode of Transport</strong> DocType in the <em>Clearing</em> module of ERPNext is used to define various transport methods such as <strong>Air</strong>, <strong>Sea</strong>, <strong>Road</strong>, and <strong>Rail</strong>. Each mode includes structured child tables to define document requirements at different clearance stages like Clearing File, TRA, Port Clearance, etc.</p>

<h2>2. Key Features</h2>
<ul>
  <li>Define standard transport modes.</li>
  <li>Link clearance document types per stage using child tables.</li>
  <li>Supports validation and automation scripts.</li>
  <li>Improves traceability and standardization.</li>
</ul>

<h2>3. Pre-Requisites</h2>
<ul>
  <li>The <strong>Clearing</strong> module must be installed.</li>
  <li><strong>Clearing Document Type</strong> DocType must be defined.</li>
  <li>Child Tables must be created: <code>clearing_file_document</code>, <code>tra_clearance_document</code>, <code>port_clearance_document</code>, etc.</li>
</ul>

<h2>4. Step-by-Step Usage</h2>

<h3>A. Create a New Transport Mode</h3>
<ol>
  <li>Go to <strong>Clearing &gt; Mode of Transport</strong>.</li>
  <li>Click <strong>New</strong>.</li>
  <li>Enter a transport method in the <strong>Name</strong> field (e.g., <em>Sea</em>).</li>
  <li>Click <strong>Save</strong>.</li>
</ol>

<h3>B. Add Required Clearance Documents</h3>
<ol>
  <li>Under any document table (e.g., <em>Port Clearance Document</em>), click <strong>Add Row</strong>.</li>
  <li>Select a <strong>Clearing Document Type</strong> (e.g., Bill of Lading).</li>
  <li>Repeat for other stages as needed.</li>
  <li>Click <strong>Save</strong>.</li>
</ol>

<h2>5. Troubleshooting (Common Errors and Resolutions)</h2>
<table>
  <thead>
    <tr>
      <th>Issue</th>
      <th>Cause</th>
      <th>Resolution</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Cannot save transport mode</td>
      <td>Missing required <code>Name</code> field</td>
      <td>Enter a value for Name</td>
    </tr>
    <tr>
      <td>"Clearing Document Type not found"</td>
      <td>Invalid link field value</td>
      <td>Ensure the referenced document type exists</td>
    </tr>
    <tr>
      <td>Unable to delete</td>
      <td>Record is referenced elsewhere</td>
      <td>Unlink or archive it first</td>
    </tr>
  </tbody>
</table>

<h2>6. User Roles and Permissions</h2>
<table>
  <thead>
    <tr>
      <th>Role</th>
      <th>Access</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>System Manager</td>
      <td>Full (Create, Read, Write, Delete, Export, Share, etc.)</td>
    </tr>
    <tr>
      <td>Clearing Officer (optional)</td>
      <td>Custom access via Role Permissions Manager</td>
    </tr>
  </tbody>
</table>

<h2>7. Key Notes</h2>
<ul>
  <li>Child tables are optional, but recommended.</li>
  <li>Document types must exist in <code>Clearing Document Type</code>.</li>
  <li>You can add columns like "Mandatory", "Sequence", or "Notes" to enhance logic.</li>
</ul>

<h2>8. What Business Process Pain Point Does It Help Remove?</h2>
<p>Previously, transport-based clearance documentation was inconsistent and error-prone. This DocType provides:</p>
<ul>
  <li>Standardization of document requirements per transport mode.</li>
  <li>Automation opportunities for validation and workflow.</li>
  <li>Reduced compliance risk and processing delays.</li>
  <li>Better collaboration across departments (logistics, customs, etc.).</li>
</ul>

</body>
</html>